Convergence in Language Design: A Case of Lightning Striking Four Times in the Same Place
Identifieur interne : 001836 ( Main/Exploration ); précédent : 001835; suivant : 001837Convergence in Language Design: A Case of Lightning Striking Four Times in the Same Place
Auteurs : Peter Van Roy [Belgique]Source :
- Lecture Notes in Computer Science [ 0302-9743 ] ; 2006.
Abstract
Abstract: What will a definitive programming language look like? By definitive language I mean a programming language that gives good solutions at its level of abstraction, allowing computer science researchers to move on and work at higher levels. Given the evolution of computer science as a field with a rising level of abstraction, it is my belief that a small set of definitive languages will eventually exist. But how can we learn something about this set, considering that many basic questions about languages have not yet been settled? In this paper, I give some tentative conclusions about one definitive language. I present four case studies of substantial research projects that tackle important problems in four quite different areas: fault-tolerant programming, secure distributed programming, network-transparent distributed programming, and teaching programming as a unified discipline. All four projects had to think about language design. In this paper, I summarize the reasons why each project designed the language it did. It turns out that all four languages have a common structure. They can be seen as layered, with the following four layers in this order: a strict functional core, then deterministic concurrency, then message-passing concurrency, and finally shared-state concurrency (usually with transactions). This confirms the importance of functional programming and message passing as important defaults; however, global mutable state is also seen as an essential ingredient.
Url:
DOI: 10.1007/11737414_2
Affiliations:
- Belgique
- Province du Brabant wallon, Région wallonne
- Louvain-la-Neuve
- Université catholique de Louvain
Links toward previous steps (curation, corpus...)
- to stream Istex, to step Corpus: 000C18
- to stream Istex, to step Curation: 000995
- to stream Istex, to step Checkpoint: 001193
- to stream Main, to step Merge: 001857
- to stream Main, to step Curation: 001836
Le document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">Convergence in Language Design: A Case of Lightning Striking Four Times in the Same Place</title><author><name sortKey="Van Roy, Peter" sort="Van Roy, Peter" uniqKey="Van Roy P" first="Peter" last="Van Roy">Peter Van Roy</name></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:B00903E9A84AFAC782E119E01E5B47B949245D17</idno><date when="2006" year="2006">2006</date><idno type="doi">10.1007/11737414_2</idno><idno type="url">https://api.istex.fr/document/B00903E9A84AFAC782E119E01E5B47B949245D17/fulltext/pdf</idno><idno type="wicri:Area/Istex/Corpus">000C18</idno><idno type="wicri:Area/Istex/Curation">000995</idno><idno type="wicri:Area/Istex/Checkpoint">001193</idno><idno type="wicri:doubleKey">0302-9743:2006:Van Roy P:convergence:in:language</idno><idno type="wicri:Area/Main/Merge">001857</idno><idno type="wicri:Area/Main/Curation">001836</idno><idno type="wicri:Area/Main/Exploration">001836</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">Convergence in Language Design: A Case of Lightning Striking Four Times in the Same Place</title><author><name sortKey="Van Roy, Peter" sort="Van Roy, Peter" uniqKey="Van Roy P" first="Peter" last="Van Roy">Peter Van Roy</name><affiliation wicri:level="4"><country xml:lang="fr">Belgique</country><wicri:regionArea>Université catholique de Louvain, B-1348, Louvain-la-Neuve</wicri:regionArea><orgName type="university">Université catholique de Louvain</orgName><placeName><settlement type="city">Louvain-la-Neuve</settlement><region type="region" nuts="1">Région wallonne</region><region type="province" nuts="1">Province du Brabant wallon</region></placeName></affiliation><affiliation wicri:level="1"><country wicri:rule="url">Belgique</country></affiliation></author></analytic><monogr></monogr><series><title level="s">Lecture Notes in Computer Science</title><imprint><date>2006</date></imprint><idno type="ISSN">0302-9743</idno><idno type="eISSN">1611-3349</idno></series><idno type="istex">B00903E9A84AFAC782E119E01E5B47B949245D17</idno><idno type="DOI">10.1007/11737414_2</idno><idno type="ChapterID">Chap2</idno><idno type="ChapterID">2</idno></biblStruct></sourceDesc></fileDesc><profileDesc><textClass></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">Abstract: What will a definitive programming language look like? By definitive language I mean a programming language that gives good solutions at its level of abstraction, allowing computer science researchers to move on and work at higher levels. Given the evolution of computer science as a field with a rising level of abstraction, it is my belief that a small set of definitive languages will eventually exist. But how can we learn something about this set, considering that many basic questions about languages have not yet been settled? In this paper, I give some tentative conclusions about one definitive language. I present four case studies of substantial research projects that tackle important problems in four quite different areas: fault-tolerant programming, secure distributed programming, network-transparent distributed programming, and teaching programming as a unified discipline. All four projects had to think about language design. In this paper, I summarize the reasons why each project designed the language it did. It turns out that all four languages have a common structure. They can be seen as layered, with the following four layers in this order: a strict functional core, then deterministic concurrency, then message-passing concurrency, and finally shared-state concurrency (usually with transactions). This confirms the importance of functional programming and message passing as important defaults; however, global mutable state is also seen as an essential ingredient.</div></front></TEI><affiliations><list><country><li>Belgique</li></country><region><li>Province du Brabant wallon</li><li>Région wallonne</li></region><settlement><li>Louvain-la-Neuve</li></settlement><orgName><li>Université catholique de Louvain</li></orgName></list><tree><country name="Belgique"><region name="Région wallonne"><name sortKey="Van Roy, Peter" sort="Van Roy, Peter" uniqKey="Van Roy P" first="Peter" last="Van Roy">Peter Van Roy</name></region><name sortKey="Van Roy, Peter" sort="Van Roy, Peter" uniqKey="Van Roy P" first="Peter" last="Van Roy">Peter Van Roy</name></country></tree></affiliations></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Musique/explor/MozartV1/Data/Main/Exploration
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 001836 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Main/Exploration/biblio.hfd -nk 001836 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Wicri/Musique
|area= MozartV1
|flux= Main
|étape= Exploration
|type= RBID
|clé= ISTEX:B00903E9A84AFAC782E119E01E5B47B949245D17
|texte= Convergence in Language Design: A Case of Lightning Striking Four Times in the Same Place
}}
| This area was generated with Dilib version V0.6.20. |  |